Transaction card with integrated usb device

ABSTRACT

A transaction card is provided for communicating with a computing device. The transaction card may comprise a computer interface device, at least one memory, at least one processor, and a card reader module. The card reader module configured to receive, from the computing device through the computer interface device, a first data packet comprising a request associated with a transaction, the first data packet being compatible with an interface protocol. The card reader module may process the first data packet to generate a second data packet compatible with the payment authentication protocol; provide the second data packet to the processor; receive, from the processor, a third data packet comprising a response to the request; process the third data packet to generate a fourth data packet based on the response, the fourth data packet compatible with the interface protocol; and transmit, to the computer interface device, the fourth data packet.

TECHNICAL FIELD

The disclosed embodiments generally relate to a transaction card, andparticularly, to a transaction card with integrated interfacecomponents, such as a Universal Serial Bus (USB) device, that can beplugged into a computing device.

BACKGROUND

Transaction cards, such as credit and debit cards, have become a primarymeans for customers to conduct financial transactions. But manytransaction card providers are moving away from using magnetic striptechnology and now include more advanced transaction components attachedto or embedded within a transaction card. For example, some transactioncards now include microchips (e.g., microchips based on the Europay,MasterCard, and Visa standard, also called “EMV chips”) that moresecurely and efficiently manage card and customer information.

In recent years, online retail or “e-commerce” has become increasinglypopular and many consumers complete purchases online, for example,through a personal computer. These online transactions, however, oftendon't allow for the additional security benefits provided by smart cardswith EMV as standard computers, such as a desktop or laptop computer,have no way of connecting directly to a smart card. Therefore, in suchonline transactions, an online retailer has no way of verifying whetherthe person making the purchase is in actual physical possession of thecard, which may present security risks both for the online retailer andthe cardholder. To provide such functionality, conventional techniquesrequire a user to purchase and use a separate auxiliary card readerdevice. These card readers, however, add additional expense andinconvenience for customers making online purchases.

Accordingly, in view of these and other deficiencies in existingtechniques, technological solutions are needed for conducting atransaction using a transaction card on a standard computer. Solutionsshould advantageously allow the transaction card to be plugged directlyinto the computing device using a widely used type of connection port.Further, the transaction card should be configured such that thecardholder may make card-present transactions, for example, using an EMVchip on the card.

SUMMARY

The disclosed embodiments relate to a transaction card with anintegrated USB or other interface device.

In one embodiment, the transaction card may comprise a computerinterface device configured to connect to a port of a computing device;at least one memory device storing instructions; at least one processorfor executing the instructions to conduct a verification process for atransaction using a payment authentication protocol; and a card readermodule communicatively coupled to the computer interface device and theat least one processor. The card reader module may be configured toreceive, from the computing device through the computer interfacedevice, a first data packet comprising a request associated with thetransaction, wherein the first data packet is compatible with aninterface protocol. The card reader module may further be configured toprocess the first data packet to generate a second data packetcompatible with the payment authentication protocol; provide the seconddata packet to the at least one processor; receive, from the at leastone processor, a third data packet comprising a response to the request;process the third data packet to generate a fourth data packet based onthe response, the fourth data packet compatible with the interfaceprotocol; and transmit, to the computer interface device, the fourthdata packet.

In another embodiment, a method for completing a transaction bytransaction card is disclosed. The method may comprise receiving, from acomputing device through a computer interface device, a first datapacket comprising a request associated with a transaction, thetransaction being associated with a payment authentication protocol, thefirst data packet being compatible with an interface protocol. Themethod may also comprise processing, by a card reader module disposed onthe transaction card, the first data packet to generate a second datapacket compatible with the payment authentication protocol; processingthe request using a secure element disposed on the transaction card;generating a third data packet based on the processing of the request;processing, by the card reader module, the third data packet to generatea fourth data packet compatible with the interface protocol; andtransmitting, to the computing device through the computer interfacedevice, the fourth data packet.

In another embodiment, the transaction card may comprise a computerinterface device configured to connect to a port of a computing device;at least one processor configured to execute a transaction associatedwith a payment authentication protocol; and a card reader module. Thecard reader module may be configured to detect that the computerinterface device has been connected to the port of the computing device;receive, in response to the detected connection, a first requestassociated with the transaction, the first request being associated witha data communication protocol; process the first request to generate asecond request being compatible with the payment authenticationprotocol; receive, from the at least one processor, a first responsebased on the second request, wherein the first response is compatiblewith the payment authentication protocol; process the first response togenerate a second response, the second response being associated withthe data communication protocol; and transmit, to the computer interfacedevice, the fourth data packet to complete the transaction.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory only,and are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary transaction environment foruse with a transaction card in accordance with the disclosedembodiments.

FIG. 2 is a block diagram of an exemplary transaction card with anintegrated interface device in accordance with disclosed embodiments.

FIGS. 3A and 3B illustrate an exemplary transaction card with anintegrated interface device on a corner of the transaction card inaccordance with disclosed embodiments.

FIG. 4 illustrates an alternate configuration of a transaction card withan integrated interface device in accordance with disclosed embodiments.

FIG. 5 illustrates an exemplary transaction card with a slidableintegrated interface device in accordance with disclosed embodiments.

FIG. 6 illustrates an exemplary transaction card with a rotatableintegrated interface device in accordance with disclosed embodiments.

FIG. 7 illustrates an exemplary foldable transaction card with anintegrated interface device in accordance with disclosed embodiments.

FIG. 8 is a flowchart illustrating an exemplary process for completing atransaction using a transaction card with an integrated interface devicein accordance with disclosed embodiments.

FIG. 9 is a flowchart illustrating an exemplary process ofauthenticating a user consistent with the disclosed embodiments.

DETAILED DESCRIPTION

The present disclosure provides a transaction card with an integratedUniversal Serial Bus (USB) or other computer interface device such thatthe transaction card may be inserted into a port of a computing device.The transaction card may also comprise an integrated card reader moduleconfigured to provide a communication interface between the USB device(or other such interface device) and the internals of the transactioncard, as described in greater detail below.

Interfacing directly with the computing device may overcome severaltechnological problems relating to security, efficiency, convenience,and functionality associated with use of the transaction card. Forexample, the integrated USB device may allow an online retailer toaccept a payment through USB or another protocol rather than requiringthe customer to type in their 16-digit card number on the website. Ifthe transaction card is compatible with an EMV cryptographic exchange,the retailer may accept the payment as a card-present transaction,thereby reducing the risk of fraud. Further, the transaction card mayallow for better or additional means of verifying a cardholder'scredentials, for example, as a form of two-factor authentication. Acryptographic exchange between the transaction card and the computingdevice allows the computing device or an application on the computingdevice to verify that the user of the transaction is in physicalpossession of the card, thereby enhancing security.

As used herein, “cardholder” may refer to an authorized user of atransaction card. For example, a cardholder may be a customer of afinancial institution, such as a bank, a credit union, a credit cardissuer, or other type of financial service entity that generates,provides, manages, and/or maintains financial service accounts for oneor more customers. The cardholder may be associated with a financialservice account, such as a credit card account, checking account,savings account, loan account, reward account, and any other type offinancial service account known to those skilled in the art. Thecardholder and/or financial service account may be associated withphysical transaction cards, such as a credit or debit cards that acardholder may carry on their person and be authorized to use to performfinancial service transactions, for example, at a point of sale (POS)terminal, through an online transaction, at an automated teller machine(ATM), etc. In some embodiments, a cardholder may be a customer of abusiness entity, such as a retail establishment, restaurant, onlineretailer, etc., such that the customer is associated with an accountwith the business entity (e.g., an Amazon™ account, retail account,account associated with a gift card balance, etc.).

Additional aspects of the disclosed embodiments are set forth below inthis disclosure. Reference will now be made in detail to exemplaryembodiments, examples of which are illustrated in the accompanyingdrawings and disclosed herein. Wherever convenient, the same referencenumbers will be used throughout the drawings to refer to the same orlike parts. In the following description, certain aspects andembodiments of the present disclosure will become evident. It should beunderstood that the disclosure, in its broadest sense, could bepracticed without having one or more features of these aspects andembodiments. It should also be understood that these aspects andembodiments are merely exemplary.

FIG. 1 is a block diagram of an exemplary transaction environment 100for use with a transaction card in accordance with the disclosedembodiments. Environment 100 may comprise a transaction card 110 with anintegrated interface device (e.g., a USB device), a computing device120, and a network 130. In some embodiments, environment 100 may furthercomprise an auxiliary device 140. It should be appreciated, however,that transaction environments 100 consistent with the disclosedembodiments may include additional and/or alternative components thanthose shown in FIG. 1.

Transaction card 110 may be any physical card product configured toprovide information, such as financial information (e.g., card numbers,account numbers, etc.), quasi-financial information (e.g., rewardsbalance, discount information, etc.) and/or individual-identifyinginformation (e.g., name, address, etc.), to another device. Examples oftransaction cards include credit cards, debit cards, gift cards, rewardscards, frequent flyer cards, merchant-specific cards, discount cards,identification cards, and driver's licenses, but are not limitedthereto. As shown in FIG. 1, transaction card 110 may be configured tobe inserted into a port, such as a USB port, of computing device 120 toprovide a communication interface between the transaction card 110 andcomputing device 120. In some embodiments, transaction card 110 mayfurther be configured to communicate with other devices, such asauxiliary device 140 or other computing devices connected to network130.

Computing device 120 may be any device capable of communicating withtransaction card 110. In some embodiments, computing device 120 may be apersonal computer such a desktop or laptop computer and may have one ormore ports for receiving transaction card 110. Computing device 120 maybe various other devices, such as an a handheld device (e.g., a mobilephone, a tablet, or a notebook), a wearable device (e.g., a smart watch,smart jewelry, an implantable device, a fitness tracker, smart clothing,a head-mounted display, etc.), an IoT device (e.g., smart home devices,industrial devices, etc.), an automotive computer, a gaming console,and/or various other devices capable of processing and/or receiving datafrom transaction card 110. In some embodiments, as discussed furtherbelow, computing device 120 may be used for completing an onlinetransaction, such as a purchase at a website. Accordingly, computingdevice 120 may include one or more network adaptors or communicationdevices and/or interfaces (e.g., WiFi, Bluetooth®, RFID, NFC, RF,infrared, Ethernet, etc.) to communicate through network 130. Computingdevice 120 may further include one or more input/output devices, such asa keyboard, mouse, trackball, touch pad, touch screen, stylus, display,speakers, camera, physical ports, and/or the like. In some aspects,computing device may have similar or the same components as transactioncard 110.

Network 130 may be any type of network that facilitates communicationsand data transfer between components of transaction environment 100,such as, for example, computing device 120, auxiliary device 140, and/orother computing components connected to network 130. Such communicationsmay take place across various types of networks, such as the Internet, awired Wide Area Network (WAN), a wired Local Area Network (LAN), awireless WAN (e.g., WiMAX), a wireless LAN (e.g., IEEE 802.11, etc.), amesh network, a mobile/cellular network, an enterprise or private datanetwork, a storage area network, a virtual private network using apublic network, a nearfield communications technique (e.g., Bluetooth™,Near Field Communication, infrared, etc.), or various other types ofnetwork communications. In some embodiments, the communications may takeplace across two or more of these forms of networks and protocols.

Computing device 120 may communicate with one or more servers or othercomputing devices (not shown) using network 130. For example, computingdevice 120 may access a server associated with an online retailer. Auser of computing device 120 may insert transaction card 110 into a portof computing device 120 to complete a purchase through the onlineretailer. Computing device 120 may be configured to access informationassociated with transaction card 110, including an account number,expiration date, cardholder name, cardholder address, or other financialor identification information. Computing device 120 may thereforeexecute a payment using transaction card 110 without requiring a user toenter payment information such as their account number. Further,computing device 120 and transaction card 110 may enable the onlineretailer to accept a card-present payment using transaction card 110.For example, computing device 120 may be configured to execute an EMVcryptographic exchange using transaction card 110.

In certain embodiments, environment 100 may further comprise anauxiliary device 140. Auxiliary device 140 may be any device capable ofcommunicating with transaction card 110 wirelessly or via a remoteconnection (e.g., over network 130). In some embodiments, auxiliarydevice 140 may be a mobile device that is associated with thecardholder. It is understood however, that auxiliary device 140 may bevarious other devices, including those described above with respect tocomputing device 120. In some embodiments, auxiliary device 140 may beused to further authenticate a user or facilitate a transaction, asdescribed below with respect to process 900. In some embodiments,auxiliary device may contain similar or the same components astransaction card 110 or computing device 120.

FIG. 2 is a block diagram of an exemplary transaction card 110 with anintegrated interface device in accordance with disclosed embodiments.Transaction card 110 may comprise various components for performing atransaction, as shown in FIG. 2. Transaction card 110 may comprise oneor more computer interface devices 210, such as a USB device, a smartcard contact 220, a processor 230, memory 240, secure element 250, acard reader module 260, and a communication component 270. It should beappreciated, however, that transaction card 110 may include additionaland/or alternative components than those shown in FIG. 2. It isunderstood that one or more of the described components may comprisemultiple components or subcomponents. Further, it is understood that insome instances, one or more of the described components may be combinedinto a single component.

Computer interface device 210 may be any device or element forconnecting with a computing device, such as computing device 120. Insome embodiments, computer interface device 210 may be a USB connector(e.g., USB-A, USB-B, USB-C, Lightning, Micro-A, Micro-B, Mini-A, Mini-B,etc.). Computer interface device 210 may be various other forms ofconnectors, including DVI, DisplayPort, eSATA, Firewire, 30-pin, HDMI,etc. In some embodiments, computer interface device 210 may communicatewith computing device 120 through a memory card slot. Accordingly,computer interface device 210 may be compatible with a memory cardfamily, such as MultiMediaCard (MMC), Secure Digital (SD), Memory Stick,XQD, XD, etc. Various other forms of connectors may be provided and thepresent disclosure is not limited to the connectors described above.Computer interface device 210 may further be configured to receive powerfrom computing device 120 for powering processor 230, card reader module260 and various other components of transaction card 110.

Smart card contact 220 may be configured to make physical contact with atraditional smart card reader device and may be communicativelyconnected to processor 230 to facilitate transactions or authenticationprotocols. For example, smart card contact 220 may be used to makefinancial transactions through a card reader, for example, at a merchantdevice, a POS device, a chip reader, an ATM, etc. Computer interfacedevice 210 may be used instead of smart card contact 220 whentransaction card 110 is inserted into computing device 120, thusobviating the need for a separate card reader device.

Processor (or processors) 230 may be configured to process and exchangeinformation for executing a transaction and/or authentication request.Processor 230 may comprise a computer, a microprocessor, a processingunit, an integrated circuit, an application specific integrated circuit(ASIC), or the like. Processor 230 may be configured to run applicationsstored in memory 240 (e.g., as stored in instructions) for executing atransaction or authentication process. For example, processor 230 mayperform a card authentication process, cardholder verification process,or transaction authorization process associated with a transaction.Processor 230 may communicate with computing device 120 through computerinterface device 210 and card reader module 260. Processor may also beable to communicate with other computing devices, such as those throughcommunication component 270.

Memory (or memories) 240 may include one or more storage devicesconfigured to store instructions to perform operations related to atransaction. Memory 240 may be any form of storage device that may beincluded on a transaction card, such as a dynamic random access memory(DRAM), a static random access memory (SRAM), a flash memory, anembedded multi-media controller (eMMC), an electrically erasableprogrammable read-only memory (EEPROM), or the like. Memory 240 may beconfigured to store applications, such as Europay Mastercard® Visa®(EMV) applications, that provide instructions for completing atransaction or a cardholder verification process. Memory 240 maycomprise other data, such as lifecycle information, intellectualproperty information, manufacturer information, personalization data(e.g., account numbers, keys, transaction counters, etc.), biometricinformation (e.g., fingerprint templates, etc.), or the like.

Transaction card 110 may further comprise a secure element 250, whichmay store sensitive data and perform secure operations depending on theapplications supported by transaction card 110. For example, secureelement 250 may store a cryptographic key which may be used to digitallysign information received from processor 230. The signed information maybe used to create unique transaction data for use in a cardauthentication process. In some embodiments, secure element 250 may becombined with processor 230 and/or memory 240. For example, memory 240may store data for authenticating transaction card 110 in a securelocation.

Transaction card 110 may further comprise a card reader module 260 forinterfacing between computer interface device 210 and processor 230 orother computing components of environment 100. In some embodiments, datareceived through computer interface device 210 may not be directlycompatible with processor 230 or other components of transaction card110 (e.g., communication component 270). Accordingly, card reader module260 may convert data received through computer interface device 210 intodata that may be read and processed by processor 230 and/or othercomponents of card 110. Card reader module 260 may also convert data ina reciprocal manner, such as translating data associated with processor230 or another component of transaction card 110 into a formatcompatible with computer interface device 210 (e.g., to facilitatecommunication with computing device 120 or another such computingdevice). For example, transaction card 110 may conform to a smart cardstandard, such as ISO/EIC 7816 and, accordingly, processor 230 may beconfigured to communicate via Application Protocol Data Units (APDUs)conforming to ISO/EIC 7816-4. Card reader module 260 may comprise amemory device for storing instructions for converting the data and aprocessor for executing the instructions. Card reader module 260 mayperform various functions that would otherwise be performed by aseparate physical card reader. Therefore, transaction card 110 mayinterface directly with computing device 120, thereby obviating the needfor an auxiliary card reader device.

As an illustrative example, if computer interface device 210 is a USBconnection, computing device 120 may send a request to transaction card110 according to a USB protocol. The request may comprise a request fortransaction card 110 to perform a card verification process to verifythat the person trying to complete a transaction on computing device 120is in actual physical possession of the card. The request may betransmitted in the form of one or more data packets according to the USBprotocol. In addition to data associated with the request, the packetsmay include, for example, control information (e.g., source,destination, length of data, etc.), error detection and correction bits,or the like. Card reader module 260 may be configured to interpret thedata packets and convert them to a format compatible with components ofthe transaction card 110, for example, into a command APDU. As anexample, card reader module 260 may process the received request toinclude a mandatory header (including a class byte, an instruction byte,parameter bytes, etc.), to reformat data from one format to another, orany other processing steps required to format the received data.Similarly, when card reader module 260 receives data from processor 230,card reader module 260 may process the data and transmit it to computingdevice 120 (e.g., via computer interface device 210). For example, cardreader module 260 may receive a response ADPU from processor 230including a mandatory trailer comprising a status word. Card readermodule 260 may process the response ADPU and convert it into datapackets conforming to the USB protocol associated with computerinterface device 210.

In some embodiments, transaction card 110 may include communicationcomponent 270 and/or various other components. Communication component270 may be configured to provide an additional or alternate channel forcommunication with a device, such as computing device 120 or auxiliarydevice 140. For example, communication component 270 may be ashort-range wireless device (e.g., Bluetooth®, NFC, RF, RFID, etc.).Communication component 270 may be powered by a connection withcomputing device 120 through computer interface device 210.Communication component 270 may be configured to perform additionalverification of the transaction card or the cardholder, as describedbelow with respect to process 900, or various other functions. In someembodiments, communication component may send a notification, statusinformation or other data to auxiliary device 140, which may be a mobiledevice of the cardholder. In certain aspects, communication componentmay be configured to transmit and receive data over network 130 toperform processes consistent with the disclosed embodiments.

Transaction card 110 may be constructed of various materials suitablefor a transaction card. For example, transaction card 110 may bemanufactured out of plastic such as polycarbonate (PC) or polyvinylchloride (PVC). Various other materials may also be used, including(soft touch plastic, aluminum, fiber composite materials, resin, etc.).In some embodiments, a card frame (not shown) disposed on transactioncard 110 may include additional material features, such as coverings(e.g., a silicone overmold), veneers (e.g., a wooden veneer), finishes(e.g. an oil-slick aluminum finish), or the like.

The physical properties of transaction card 110 (e.g., size,flexibility, location of various components included in the card) maymeet the various international standards, including, for example,ISO/IEC 7810, ISO/IEC 7811, ISO/IEC 7812, ISO/IEC 7813, ISO/IEC 7816,ISO 8583, ISO/IEC 4909, and ISO/IEC 14443. As shown in FIG. 3A, forexample, transaction card 110 may have a width (W) of approximately85.60 mm, a height (H) of approximately 53.98 mm, and a thickness ofapproximately 0.76 mm, as specified in ISO/IEC 7810. In someembodiments, transaction card 110 may be thicker as to accommodatevarious features of transaction card 110, such as computer interfacedevice 210. It would be apparent to one of skill in the art that otherdimensions and layouts of card components of transaction card 110 arepossible as well.

As described above, computer interface device 210 may be configured toconnect to a variety of ports of a computer, such as USB-A, USB-B,USB-C, Lightning, Micro-A, Micro-B, Mini-A, Mini-B, or the like. Thephysical properties of computer interface device 210 (e.g., size,flexibility, location of various components included in the card) maymeet various standards for data connectors, such as various USBstandards. In some embodiments, computer interface device 210 may beconfigured to be substantially the same thickness as transaction card110. In some embodiments, computer interface device may be a shieldlessdevice, configured to fit into a USB port. For example, computerinterface device may have a similar size and configuration as a userdata protocol (UDP) style flash drive and may be insertable into astandard USB port. Accordingly, computer interface device 210 may have athickness of approximately 1 mm.

Consistent with the disclosed embodiments, transaction card 110 may havevarious configurations for integrating computer interface device 210.For example, computer interface device 210 may be disposed in variouslocations and configurations on transaction card 110. FIGS. 3A and 3Billustrate an exemplary transaction card 110 with an integrated USBdevice 210 on a corner of the card in accordance with disclosedembodiments. For example, as shown in FIGS. 3A and 3B, one corner oftransaction card 110 may have a cutout on one corner to include computerinterface device 210.

Computer interface device 210 may be configured such that the overallcard dimensions still comply with one or more of the various standardsdescribed above. For example, interface device 210 may still fit withinthe overall width (W) of approximately 85.60 mm and height (H) ofapproximately 53.98 mm, as shown in FIG. 3A. Computer interface device210 may have one or more contact points 301 for interfacing withcomputing device 120. Contact points 301 may communicatively connect tocorresponding pins or plates of a port in computing device 120 tofacilitate the transfer of data between computing device 120 andtransaction card 110. Transaction card 110 may also include smart cardcontact 220, which may allow smart card transactions, such as an EMVpayment, as described above. For example, smart card contact 220 may beconfigured such that transaction card 110 may be inserted into a smartcard reader to perform the smart card transaction. Accordingly, thephysical properties of smart card contact 220 may comply with one ormore international standards such as ISO/IEC 7816, ISO/IEC 14443 or thelike. In some embodiments, smart card contact 220 may be disposed inproximity to an edge of transaction card 110 opposite to or distancedfrom an edge on which computing interface device 210 is disposed. Insome embodiments, for example, a first distance between smart cardcontact 220 and a first edge (e.g., the edge of transaction card 110subtended by height H in FIG. 3A) may be less than a distance betweensmart card contact 220 and computing interface device 210. Additionallyor alternatively, a second distance between smart card contact 220 and asecond edge (e.g., the edge subtended by width W in FIG. 3A) may be lessthan the distance between smart card contact 220 and computing interfacedevice 210.

FIG. 3B shows a reverse side of transaction card 110 from the side shownin FIG. 3A. Transaction card 110 may have one or more additionalcomponents to facilitate or improve the use of transaction card 110. Forexample, transaction card 110 may have a magnetic strip 310, a hologram311, a signature block 312, an imprinted name and/or account number, anexpiration date, a card verification value (CVV) code, or various othercard features.

Transaction card 110 may also have various other configurations orcomponents for integrating card interface device 210. FIG. 4 illustratesan alternate configuration of a transaction card 110 with an integratedinterface device 210 (e.g., a USB device) in accordance with disclosedembodiments. In this embodiment, a side of transaction card 110 may becut out, shortened, or removed to include computer interface device 210.Various other shapes or arrangements may also be used. For example,transaction card 110 may have a cutout on the bottom of the card forincluding computer interface device 210. The cutout may also have othershapes, such as a curved or geometric shape, to integrate computerinterface device 210 and provide sufficient clearance such that computerinterface device may be inserted into computing device 120. Transactioncard 110 may also include smart card contact 220 disposed and placed ina manner as described above (e.g., distanced from an edge of transactioncard 110 on which computing interface device 210 is disposed).

FIG. 5 illustrates an exemplary transaction card 110 with a slidableintegrated interface device 210 (e.g., a USB device) in accordance withdisclosed embodiments. Accordingly, transaction card 110 may have atrack component 501 which may allow computer interface device 210 toslide from a retracted position, where computer interface device 210 issubstantially or completely contained within the outer perimeter oftransaction card 110, to an extended position (e.g., as shown in FIG. 5)for inserting into computing device 120. Track component 510 maycomprise a cutout portion of transaction card 110 to receive computerinterface device 210. Track component 510 may have additional featuresto guide computer interface device 210. For example, the inner surfaceof the cutout may comprise grooves for receiving a corresponding elementof the sliding portion of transaction card 110. In some embodiments,transaction card 110 may have additional features to facilitate slidingcard interface device 210 between its retracted and extended position.For example, the sliding portion of transaction card 110 may comprise arubberized or otherwise grippable surface to facilitate sliding thecomputer interface device. Similarly, transaction card may include oneor more ridges, bumps, grooves or other features to increase grip.Various other locations, sizes, and configurations of a slidablecomputer interface device 210 may be used. Transaction card 110 may alsoinclude smart card contact 220 disposed and placed in a manner asdescribed above (e.g., distanced from an edge of transaction card 110 onwhich computing interface device 210 is disposed).

In some embodiments, some or all of the components of transaction card110 described with respect to FIG. 2 may be included on a slidingportion of transaction card 110. For example, smart card contact 220 aswell as various internal components (e.g., processor 230, card readermodule 260, memory 240, etc.) may be included on the sliding portion. Insuch embodiments, track component 510 would not need to accommodatecommunication between the sliding portion and nonsliding portion oftransaction card 110. In other embodiments, transaction card 110 mayinclude wires for communicatively coupling computer interface device 210with other components on transaction card 110. In some embodiments,track component 510 may have one or more corresponding contact points,pins, plates, grooves, etc. for providing a communication interfacebetween the sliding and non-sliding portions of transaction card 110.

FIG. 6 illustrates an exemplary transaction card 110 with a rotatableintegrated interface device 210 (e.g., a USB device) in accordance withdisclosed embodiments. As shown in FIG. 6, computer interface device 210may be rotatably connected to a portion of transaction card 110 (e.g.,via rotating component 601 discussed below) such that interface device210 may rotate from an initial position to an extended position,allowing insertion of computer interface device 210 into computingdevice 120. In some embodiments, the initial position may be wholly orsubstantially contained without the outer perimeter of transaction card110, and the extended position may be orthogonal to a first edge, secondedge, or first surface of transaction card 110. For example, computerinterface device 210 may be rotated to provide sufficient clearance suchthat other portions of transaction card 110 do not prevent insertioninto computing device 120. In some embodiments, computer interfacedevice 210 may be disposed on the nonrotating portion of transactioncard 110 and the rotating portion may, for example, act as a guard orshield for computer interface device 210.

Accordingly, transaction card 110 may have one or more rotatingcomponents 601 facilitating the rotatable connection of interface device210 to transaction card 110. In some embodiments, rotating componentsmay comprise a revolute joint, pins, hinges, ball-and-socket joints,bearings, etc. for rotatably coupling or connecting interface device 210to transaction card 110. Similar to track component 501 described above,rotating component 601 may have various communication components, suchas wires or corresponding contact points, pins, plates, grooves, etc.,for providing a communication interface between the rotating andnonrotating portions of transaction card 110 (e.g., with interfacedevice 210). In other embodiments, other components of transaction card110 (e.g., processor 230, card reader module 260, memory 240, smart cardcontact 220, etc.) may be disposed on the same portion of transactioncard 110 as computer interface device 210 such that no communicationthrough rotating component 601 is necessary.

Transaction card 110 may also have one or more foldable portions tofacilitate the insertion of computer interface device 210 into computingdevice 120. FIG. 7 illustrates an exemplary foldable transaction card110 with an integrated interface device 210 (e.g., USB device) inaccordance with disclosed embodiments. Transaction card may beconfigured such that, when laid flat in an unfolded position, computerinterface device 210 is contained within the perimeter of transactioncard 110. As shown in FIG. 7, transaction card 110 may be foldable suchthat computer interface device 210 protrudes outward and is therebyinsertable into computing device 120 when foldable component 710 is in afolded position. Accordingly, transaction card 110 may have one or morefoldable component(s) 701 to facilitate the folding of transaction card110. In some embodiments, foldable component 701 may comprise a flexibleportion, which may be constructed of a flexible plastic (e.g., athermoplastic elastomer), rubber, or the like. Foldable component 701may also be a hinged component, and may, for example, comprise a pin toprovide rotating interface between the two portions of transaction card110. In some embodiments, foldable component 701 may be a living hingeand the two portions of transaction card 110 may be integrallyconnected. Transaction card 110 may also comprise one or more cutouts702 for receiving computer interface device 210 when transaction card110 is in the unfolded position. Transaction card 110 may be configuredthat smart card contact 220 may be used for completing transactionsthrough a card reader device. For example, smart card contact 220 may bedisposed on a substantially rigid portion of the transaction card 110such that it can be inserted into a card reader, as shown. Additionallyor alternatively, smart card contact 220 may be disposed and placed in amanner as described above (e.g., in closer proximity to one or moreedges of transaction card 110 than an edge formed when foldablecomponent 701 is in a folded position).

FIG. 8 is a flowchart illustrating an exemplary process 800 forcompleting a transaction using a transaction card (e.g., transactioncard 110) with an integrated interface device (e.g., interface device210 such as a USB device) in accordance with disclosed embodiments.Process 800 may be performed by the transaction card inserted into acomputing device (e.g., computing device 120) or computing device 120itself. Thus, while certain aspects of the following embodiments aregenerally described from the perspective of transaction card 110, itshould be appreciated that reciprocal or the same processes may takeplace on corresponding components of computing device 120, or any othercomputing device connected to network 130 (e.g., a remote serverassociated with a financial institution).

In certain aspects, the transaction card 110 may comprise the computerinterface device configured to connect to a port of the computing device(e.g., a USB port, HDMI port, SD port, or other such port). Thetransaction card may further comprise at least one memory device (e.g.,memory 240) storing instructions and at least one processor (e.g.,processor 230) for executing the instructions to conduct a verificationprocess for a transaction using a payment authentication protocol. Thetransaction card may further comprise a card reader module (e.g., cardreader module 260) communicatively coupled to the computer interfacedevice and the at least one processor. Process 800 may be performed, forexample, by transaction card 110, described above. Computer interfacedevice 210 of transaction card 110 may be inserted into a port ofcomputing device 120 to perform a transaction over network 130, such asan online payment, online transaction, online balance transfer, or thelike. In some embodiments, process 800 may allow an online merchant orservice to accept payments through a USB or similar port without theneed for a card reader. Process 800 may further allow the onlinemerchant or service to accept the payment as a card-present payment, forexample through an EMV cryptographic exchange.

At step 810, process 800 may include receiving, from a computing devicethrough a computer interface device, a first data packet comprising (orpartially comprising) a request associated with a transaction (e.g., anonline transaction initiated with the computing device). The computerinterface device may comprise a connector compatible with a standardcomputing device, such as a USB connector. For example, transaction card110 may receive the first data packet from computing device 120 throughcomputer interface device 210. The transaction may be a transactionperformed on or through computing device 120, such as an online paymentconducted over network 130. The transaction may be associated with apayment authentication protocol such as an EMV payment standard or thelike. In some embodiments, the computing device may be a handheld ormobile device, such as a mobile phone. In some embodiments, card readermodule 260 and/or processor 230 may also be configured to detect thatthe computer interface device has been connected to the port of thecomputing device. In certain aspects, transaction card 110 may beconfigured to passively or actively monitor signals from one or more ofits components (e.g., computer interface device 210) to determinewhether and when computer interface device 210 becomes inserted into aport of computing device 120.

The request associated with the first data packet may be transmitted tothe transaction card 110 in order to carry out the transaction. Therequest may comprise a request for information associated with thetransaction card 110 or cardholder, such as an account number, thecardholder's name, the cardholder's address, etc. In some embodiments,computing device 120 may be configured to automatically provide thisinformation to the online retailer based on data received fromtransaction card 110 via computer interface device 210. For example,computing device 120 may automatically populate a form or webpage usingpayment or identification information received from transaction card 110via computer interface device 210 using data conversion techniquesconsistent with the disclosed embodiments. In some embodiments, therequest may also comprise a card data authentication request, forexample using Static Data Authentication (SDA), Dynamic DataAuthentication (DDA), Combined Data Authentication (CDA), or the like.In other embodiments, the request may be part of a cardholderverification request, or other function performed using the transactioncard. The request may be received by transaction card 110 through theone or more first data packets. The first data packet or packets may becompatible with an interface protocol, such as a USB protocol, asdescribed above.

In step 820, process 800 may include processing, by a card reader module(e.g., card reader module 260) disposed on the transaction card 110, thefirst data packet to generate a second data packet compatible with thepayment authentication protocol. In some embodiments, a format orprotocol associated with the first data packet may be distinct from theformat or protocol (e.g., the payment authentication protocol)associated with the second data packet. For example, the first datapacket may be compatible with a USB protocol, and card reader module 260may be configured to convert or translate the first data packet into asecond data packet with an updated format or protocol. In someembodiments, for example, the second data packet may be a command ADPUas described above. Accordingly, the second data packet may becompatible with the payment authentication protocol.

In certain aspects, for example, transaction card 110 may be configuredto identify a first protocol or format (e.g., a USB protocol) associatedwith the first data packet based on a signal received from computerinterface device 210, based on information contained in the first datapacket (e.g., recognizing an identifying header, metadata, transactiontype, etc.), based on an analysis of the received data packet or signalat card reader module 260, or based on any other similar considerationconsistent with the disclosed embodiments. Similarly, transaction card110 may identify the second format or protocol for the second datapacket based on a signal received from computer interface device 210,based on information contained in the first data packet (e.g.,indicating that the requested transaction reflects a purchasetransaction, a balance transfer, etc.), based on one or more determinedor known protocols or formats compatible with computer interface device210, card reader module 260, smart card contact 220, or any other suchconsideration consistent with the disclosed embodiments. In someaspects, transaction card 110 may store the routines and algorithms forconverting or translating data from the first protocol or format intothe second protocol or format for use by card reader module 260.Additionally or alternatively, the conversion routines may betransmitted as part of a signal or the first data packet associated withcomputer interface device 210, or may be obtained from another computingdevice (e.g., computing device 120 or another device connected tonetwork 130) via communication component 270, computer interface device210, etc.

In step 830, process 800 may include processing the request using asecure element (e.g., secure element 250) disposed on the transactioncard 110. For example, card reader module 260 may provide the seconddata packet to processor 230, which may perform step 830. As describedabove, the request may be associated with a request for information, acard data authentication request, a cardholder verification request,another process for completing the transaction, or any other requestconsistent with the disclosed embodiments. In some embodiments,transaction card 110 may further comprise a secure element 250communicatively coupled with the processor 230. The verification processmay comprise verifying, using the secure element, that the transactioncard is in physical presence of a cardholder associated with thetransaction. For example, the secure element may comprise acryptographic key which may be used to sign data provided by processor130 for authenticating transaction card 110.

In step 840, process 800 may include generating a third data packetbased on the processing of the request. For example, the third datapacket may comprise or partially comprise a response to the requestreceived from computing device 120 pertaining to a transaction. In someembodiments, the third data packet may be associated with a format orprotocol identical to one associated with the second data packet, suchas the payment authentication protocol. For example, the third datapacket may comprise a response ADPU generated by processor 130 based onthe processing in step 830.

In step 850, process 800 may include processing, by the card readermodule 260, the third data packet to generate a fourth data packetcompatible with an interface protocol. For example, card reader module260 may receive the third data packet from processor 130. Card readermodule 260 may process the third data packet to convert it to a fourthdata packet compatible with the interface protocol associated withcomputer interface device 210, such as the USB protocol described above.In some embodiments transaction card 110 may be configured to convert ortranslate data from a second format or protocol (e.g., a paymentauthentication protocol) into a first format or protocol (e.g., a USBprotocol) in a manner similar to that described above for the reciprocalconversation and translation routines. For example, transaction card maybe configured to identify the first and second formats and protocolsbased on information contained in the first, second, third, or fourthdata packets, based on a signal received from computer interface device210, card reader module 260, or any other component of transaction card110. Transaction card 110 may also store the routines and algorithms forconverting or translating data from the second protocol or format intothe first protocol or format, or additionally or alternatively may beconfigured to obtain such routines from another computing device vianetwork 130. In step 860, process 800 may include transmitting, to thecomputing device 120 through the computer interface device 210, thefourth data packet, which may enable the computing device 120 tocomplete the transaction. In some aspects, for instance, transmittingthe fourth data packet (e.g., formatted in a USB protocol) to computingdevice 120 via computer interface device 210 may facilitate and completea requested online transaction initiated at computing device 120.

In some embodiments, process 800 may be performed in the absence of atransaction. For example, transaction card 110 may be used toauthenticate a user of computing device 120 through a multifactorauthentication process. As an illustrative example, a cardholder may beattempting to login to an account, such as a financial services account,a banking account, a network account, or any other account requiringcredentials of the user. In some embodiments, transaction card 110 maybe used to provide a second form of authentication for the cardholderassociated with the account. For example, a user's physical possessionof transaction card 110 associated with the user's purported identitymay indicate that the user is who they purport to be. Accordingly, theuser may insert transaction card 110 into computing device 120 forauthenticating the identity of a user. In these embodiments, the stepsof process 800 may be similar to or the same as those above, but thevarious steps may not be associated with a transaction but rather alogin or other authentication process. Further, rather than a paymentauthentication protocol, another form of authentication protocol may beused, such as a FIDO CTAP standard (e.g., FIDO U2F, FIDO UAF, FIDO 2,etc.) or the like.

In some embodiments, transaction card 110 may be configured to performfurther authentication for the user of computing device 120 and/ortransaction card 110. In these embodiments, process 800 may comprise oneor more additional steps. Alternatively, these steps may be undertakendistinct and separate from process 800.

FIG. 9 is a flowchart illustrating an exemplary process 900 ofauthenticating a user via transaction card 110. Process 900 may beperformed by transaction card 110 or computing device 120, either inconjunction with or separate from process 800. By way of example,transaction card 110 may be configured to conduct an authenticationprocess consistent with process 900 based on and in combination with anyof the steps and embodiments consistent with process 800. By way ofnonlimiting example, transaction card 110 may be configured to conductauthentication process 900 upon determining that computer interfacedevice 210 has been inserted into a port of computing device 120 (e.g.,based on a signal received from computer interface device, card readermodule 260, etc.), upon generating a data packet (e.g., the second,third, or fourth data packets), immediately prior to completing thetransaction, prior to transmitting the fourth data packet, etc.

In step 910, for example, process 900 may include transmitting aninstruction for generating an authentication request to at least one of(i) the computing device 120, (ii) an auxiliary device 140 associatedwith a user, and/or (iii) a computing device connected to network 130(e.g., a remote server associated with a third party, with a merchantassociated with the transaction, with a server associated with anauthentication entity, etc.). For example, transaction card 110 maytransmit an instruction to provide and authentication request toauxiliary device 140, which may be a mobile phone or other deviceassociated with a cardholder of transaction card 110. In certainaspects, the authentication request may reflect a request for one ormore credentials identifying a user and may be based on one or moretransaction parameters, as discussed below.

In some embodiments, the authentication request instruction may betransmitted from the transaction card directly, for example, usingcommunication component 270. In other embodiments, the authenticationrequest instruction may be sent through computing device 120, such asvia a signal transmitted to computer interface device 210 in theappropriate format (e.g., a USB format). For example, transaction card110 may provide instructions to computing device 120 to transmit theauthentication request via network 130. In some aspects, the instructionfor generating the authentication request may comprise theauthentication request itself. Additionally or alternatively, theinstruction for generating the authentication request may cause acomponent of environment 100 (e.g., auxiliary device 140 and/orcomputing device 120) to generate the authentication request.

In step 920, process 900 may include receiving (e.g., from the computingdevice or auxiliary device) an authentication response responding to theauthentication request. For example, auxiliary device 140 and/orcomputing device 120 may display a prompt to the user. In someembodiments, the prompt may comprise a request for user to enter, input,or otherwise provide one or more credentials identifying the user (e.g.,a fingerprint, retinal or facial scan, password, pin, login, username,randomly generated n-digit code, biometric measure, MAC or IP address,etc.) via an appropriate input means consistent with the disclosedembodiments (e.g., a physical or displayed keyboard, a camera, abiometric scanner, or any other suitable peripheral). In otherembodiments, auxiliary device 140 may prompt the user to approve or denythe transaction. Auxiliary device 140 and/or computing device 120 may beconfigured to display the generated prompt from the user (e.g., via adisplay or touchscreen display associated with computing device 120and/or auxiliary device 140) and may be configured to receive theauthentication response via input means discussed herein (e.g., akeyboard, camera, etc.).

In certain aspects, the type and/or number of credentials requested inprocess 900 (e.g., as requested in the authentication request in step910 and/or provided in the authentication response in step 920) may bebased on one or more transaction parameters associated with thetransaction. For example, process 900 may generate an authenticationrequest seeking first set of credentials (e.g., an approval or denial)based on a first set of transaction parameters for a first transaction,and may seek a second set of credentials (e.g., a biographic measure,username and password, etc.) based on a second set of transactionparameters for a second transaction. In some embodiments, thetransaction parameters may comprise, but are not limited to, atransaction type, a transaction amount, a merchant identity associatedwith the transaction, a merchant type associated with the transaction, atransaction frequency (e.g., associated with a user, an accountassociated with the user, a frequency of transactions associated withtransaction card 110, computing device 120, and/or auxiliary device 140,etc.) over one or more time periods, a location associated with thetransaction (e.g., a location associated with the merchant, computingdevice 120, auxiliary device 140, transaction card 110, etc.), a type ofcomputer interface device 210 (e.g., USB), a security level associatedwith network 130 (e.g., based on an identified encryption standard for awebsite associated with an online transaction), any combination of theforegoing parameters (e.g., a transaction frequency for a particularmerchant or merchant type using transaction card 110), and so on. Thetransaction parameters may be determined and/or identified bytransaction card 110, computing device 120, auxiliary device 140, and/oranother computing device connected to network 130 to conduct processesconsistent with the disclosed embodiments.

Upon receiving a response from the user, auxiliary device 140 and/orcomputing device 120 may transmit an authentication response totransaction card 110, which may be received, for example, throughcommunication component 270 or computing device 120 via computerinterface device 210. In step 930, process 900 may includeauthenticating the user based on the authentication response received instep 920. For example, if the authentication request includes a requestfor credentials, step 930 may include verifying the received credentials(e.g., by matching the received credentials from those stored in one ormore memories in environment 100, such as in auxiliary device 140,computing device 120, or in a server connected to network 130).Accordingly, step 930 may further include accessing a resource (e.g., aserver, database, etc.) for verifying the received credentials. In otherembodiments, the authentication response may be an approval of atransaction. Computing system 120 or other components associated withenvironment 100 may take additional steps based on authenticating theuser, such as completing a transaction, logging in to a bankingapplication, etc. By way of example, the components of 100 may completethe transaction, balance transfers, etc. upon successful authenticationof the user. In some embodiments, authentication in step 930 may allowvarious other steps to be performed, including any steps performed bytransaction card 110 or computing device 120 as part of process 800. Insome embodiments, for instance, authenticating a user may causetransaction card 110 to transmit a data packet to computing device 120via computing interface device 210 to facilitate completing atransaction. In other aspects, authenticating a user may cause one ormore of the various data packets or translation routines discussed forprocess 800 to be conducted. Accordingly, using process 900, additionalverification may be performed.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as nonexclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps, combining steps, or inserting ordeleting steps.

It is appreciated that certain features of the invention, which are, forclarity, described in the context of separate embodiments, may also beprovided in combination in a single embodiment. Conversely, variousfeatures of the invention, which are, for brevity, described in thecontext of a single embodiment, may also be provided separately or inany suitable subcombination or as suitable in any other describedembodiment of the invention. Certain features described in the contextof various embodiments are not to be considered essential features ofthose embodiments, unless the embodiment is inoperative without thoseelements.

Although the invention has been described in conjunction with specificembodiments thereof, it is evident that many alternatives, modificationsand variations will be apparent to those skilled in the art.Accordingly, it is intended to embrace all such alternatives,modifications and variations that fall within the spirit and broad scopeof the appended claims.

What is claimed is:
 1. A transaction card comprising: a computerinterface device configured to connect to a port of a computing device;at least one memory device storing instructions; at least one processorfor executing the instructions to conduct a verification process for atransaction using a payment authentication protocol; and a card readermodule communicatively coupled to the computer interface device and theat least one processor, the card reader module configured to: receive,from the computing device through the computer interface device, a firstdata packet comprising a request associated with the transaction,wherein the first data packet is compatible with an interface protocol;process the first data packet to generate a second data packetcompatible with the payment authentication protocol; provide the seconddata packet to the at least one processor; receive, from the at leastone processor, a third data packet comprising a response to the request;process the third data packet to generate a fourth data packet based onthe response, the fourth data packet compatible with the interfaceprotocol; and transmit, to the computer interface device, the fourthdata packet.
 2. The transaction card of claim 1, wherein the paymentauthentication protocol is an EMV payment standard.
 3. The transactioncard of claim 1, wherein the fourth data packet enables the computingdevice to complete the transaction.
 4. The transaction card of claim 1,wherein the transaction comprises an online payment performed throughthe computing device.
 5. The transaction card of claim 1, wherein thecomputer interface device comprises a universal serial bus (USB)connector and the interface protocol comprises a USB protocol.
 6. Thetransaction card of claim 1, wherein: the transaction card furthercomprises a secure element communicatively coupled with the processor,and the verification process comprises verifying, using the secureelement, that the transaction card is in physical presence of acardholder associated with the transaction.
 7. The transaction card ofclaim 1, wherein the computing device is a mobile device.
 8. Thetransaction card of claim 1, wherein the processor is further configuredto: transmit an authentication request to at least one of (i) thecomputing device or (ii) an auxiliary device associated with a user, andexecute the transaction based on an authentication response to theauthentication request.
 9. The transaction card of claim 8, wherein theauthentication request is transmitted by a communication componentdisposed on the transaction card.
 10. The transaction card of claim 8,wherein the authentication request is transmitted to the auxiliarydevice by the computing device.
 11. A method for completing atransaction by transaction card, the method comprising: receiving, froma computing device through a computer interface device, a first datapacket comprising a request associated with a transaction, thetransaction being associated with a payment authentication protocol, thefirst data packet being compatible with an interface protocol;processing, by a card reader module disposed on the transaction card,the first data packet to generate a second data packet compatible withthe payment authentication protocol; processing the request using asecure element disposed on the transaction card; generating a third datapacket based on the processing of the request; processing, by the cardreader module, the third data packet to generate a fourth data packetcompatible with the interface protocol; and transmitting, to thecomputing device through the computer interface device, the fourth datapacket.
 12. The method of claim 11, wherein the payment authenticationprotocol is an EMV payment standard.
 13. The method of claim 11, whereinthe fourth data packet enables the computing device to complete thetransaction.
 14. The method of claim 11, wherein the transactioncomprises an online payment performed through the computing device. 15.The method of claim 11, wherein the computer interface device comprisesa universal serial bus (USB) connector and the interface protocolcomprises a USB protocol.
 16. The method of claim 11, wherein processingthe request comprises verifying that the transaction card is in physicalpresence of a cardholder associated with the transaction.
 17. The methodof claim 11, further comprising: transmitting an authentication requestto at least one of (i) the computing device or (ii) an auxiliary deviceassociated with a user, and executing the transaction based on anauthentication response to the authentication request.
 18. The method ofclaim 17, wherein the authentication request is transmitted by acommunication component disposed on the transaction card.
 19. The methodof claim 17, wherein the authentication request is transmitted throughthe computing device.
 20. A transaction card comprising: a computerinterface device configured to connect to a port of a computing device;at least one processor configured to execute a transaction associatedwith a payment authentication protocol; and a card reader moduleconfigured to: detect that the computer interface device has beenconnected to the port of the computing device; receive, in response tothe detected connection, a first request associated with thetransaction, the first request being associated with a datacommunication protocol; process the first request to generate a secondrequest being compatible with the payment authentication protocol;receive, from the at least one processor, a first response based on thesecond request, wherein the first response is compatible with thepayment authentication protocol; process the first response to generatea second response, the second response being associated with the datacommunication protocol; and transmit, to the computer interface device,the fourth data packet to complete the transaction.